This forum is closed to new posts and
responses. Individual names altered for privacy purposes. The information contained in this website is provided for informational purposes only and should not be construed as a forum for customer support requests. Any customer support requests should be directed to the official HCL customer support channels below:
RE: DXLImport ( compare data base content). ~Umberto Nongeroson 9.Dec.03 02:43 AM a Web browser Applications Development 6.0.2 CF2Windows 2000
Interesting discussion.
We considered making the DXL Importer capable of retaining the DXL-specified UNIDs when creating new notes. I think we even had internal-only versions of the Importer that did just that. After thinking it through, it was an intentional design decision to NOT retain DXL-specified UNIDs when creating new notes. Our rationale went something like this. Generally speaking, when two notes in different dbs have the same UNID, it implies the dbs are replicas and thus that the notes represent the same thing. (There are at least a couple of exceptions to this rule that I know of, but they don't change the basic point.) When a note is first created in one replica, it gets assigned an UNID, and it is the Replicator that is responsible for creating that note in other replicas, in doing so maintaining the same UNID, and other context (e.g. a revision number) that allow the Replicator to resolve conflicts, etc. When a note is modified in one replica, again the normal mechanism to make the same modifications in the other replicas is the Replicator. If DXL were to get into the business of creating the original notes or updating existing notes in replicas, it would have to be very careful to implement all of the exact same behavior and internal context that the Replicator does, or risk breaking the whole mechanism. But it really isn't the business of the DXL Importer to do this; the one component of the product that was intended for this task is the Replicator! DXL can certainly be used to create the original of a new note, but from there, it should be the Replicator that pushes it to all the other replicas. The Replicator replicates!
In short, the DXL Importer is not the Replicator, nor should it be.
I have had occasion to force a particular UNID onto a note. Am I remembering right that it is only before the first note update that this is allowed? In any event, that was from the Notes core code. So as it has been pointed out in this thread, it is doable. But it may be risky in terms of possible effects it can have on replication.
Return to top
. . . . . . . . . . . . . . . . RE: DXLImport ( compare data base c... (~Isaac Quettoog... 9.Dec.03) 
Print this page
